Skip to content

Conversation

tgross35
Copy link
Contributor

@tgross35 tgross35 commented Aug 22, 2024

Loongarch previously had a selection failure for f16 math llvm/llvm-project#93894. This was fixed in llvm/llvm-project#94456, which Rust got with the update to LLVM 19 #127513.

Enable loongarch in std/build.rs so we start running tests.

try-job: dist-loongarch64-linux
try-job: dist-loongarch64-musl

Loongarch previously had a selection failure for `f16` math [1]. This
was fixed in [2], which Rust got with the update to LLVM 19 [3].

Enable loongarch in `std/build.rs` so we start running tests.

[1]: llvm/llvm-project#93894
[2]: llvm/llvm-project#94456
[3]: rust-lang#127513
@rustbot rustbot added the T-libs Relevant to the library team, which will review and decide on the PR/issue. label Aug 22, 2024
@rustbot
Copy link
Collaborator

rustbot commented Aug 22, 2024

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 22, 2024
@tgross35
Copy link
Contributor Author

Might get a merge conflict with #128349, but we can start this rolling. Cc @heiher

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request Aug 22, 2024
Enable `f16` tests on loongarch

Loongarch previously had a selection failure for `f16` math llvm/llvm-project#93894. This was fixed in llvm/llvm-project#94456, which Rust got with the update to LLVM 19 rust-lang#127513.

Enable loongarch in `std/build.rs` so we start running tests.

try-job: dist-loongarch64-linux
try-job: dist-loongarch64-musl
@bors
Copy link
Collaborator

bors commented Aug 22, 2024

⌛ Trying commit 30641f0 with merge 247fa99...

@tgross35
Copy link
Contributor Author

Cc also @xen0n since you posted llvm/llvm-project#94456

@tgross35 tgross35 added the F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` label Aug 22, 2024
@bors
Copy link
Collaborator

bors commented Aug 22, 2024

☀️ Try build successful - checks-actions
Build commit: 247fa99 (247fa9906abe0d2416ce31fe15ac2ac518f8b89e)

@beetrees
Copy link
Contributor

The f16 tests won't pass for loongarch64-unknown-linux-gnu as the LoongArch backend is affected by llvm/llvm-project#97981 (and llvm/llvm-project#97975). (The tests aren't run in CI for LoongArch.)

@tgross35
Copy link
Contributor Author

That's right, I was forgetting that there was more to the story than just the crash. I will update the comment in #129385, otherwise I guess there isn't much to be done here.

@tgross35 tgross35 closed this Aug 22, 2024
@tgross35 tgross35 deleted the loongarch-f16 branch August 22, 2024 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants